Adapting audio output based on context

ABSTRACT

One embodiment provides a method, including: detecting, using a processor, a presence of a known device within a predetermined range; and adjusting, using the processor, an audio output volume based on the presence of the known device. Other aspects are described and claimed.

BACKGROUND

Electronic devices such as laptops, tablets, smart phones, televisionsets, audio and media players, etc. (“devices”), are used for a varietyof reasons. Commonly, users employ such devices to produce audio, e.g.,in connection with playing a song, watching a video, talking on thephone, etc.

It is typical for a user to employ more than one device at a time. It isalso common for multiple users to employ their devices at the same time.This sometimes leads to a conflict in terms of audio output, i.e., thedevices' audio outputs conflict or interfere with one another. This isnotable, for example, when multiple devices provide audio outputsimultaneously to one or more users in a room.

BRIEF SUMMARY

In summary, one aspect provides a method, comprising: detecting, using aprocessor, a presence of a known device within a predetermined range;and adjusting, using the processor, an audio output volume based on thepresence of the known device.

Another aspect provides a device, comprising: a processor; an audiooutput device operatively coupled to the processor; a memory device thatstores instructions executable by the processor to: detect a presence ofa known device within a predetermined range; and adjusting, using theprocessor, an audio output volume based on the presence of the knowndevice.

A further aspect provides a product, comprising: a storage device havingcode stored therewith, the code being executable by a processor andcomprising: code that detects a presence of a known device within apredetermined range; and code that adjusts an audio output volume basedon the presence of the known device.

The foregoing is a summary and thus may contain simplifications,generalizations, and omissions of detail; consequently, those skilled inthe art will appreciate that the summary is illustrative only and is notintended to be in any way limiting.

For a better understanding of the embodiments, together with other andfurther features and advantages thereof, reference is made to thefollowing description, taken in conjunction with the accompanyingdrawings. The scope of the invention will be pointed out in the appendedclaims.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 illustrates an example of information handling device circuitry.

FIG. 2 illustrates another example of information handling devicecircuitry.

FIG. 3 illustrates an example method of adapting audio output based oncontext.

DETAILED DESCRIPTION

It will be readily understood that the components of the embodiments, asgenerally described and illustrated in the figures herein, may bearranged and designed in a wide variety of different configurations inaddition to the described example embodiments. Thus, the following moredetailed description of the example embodiments, as represented in thefigures, is not intended to limit the scope of the embodiments, asclaimed, but is merely representative of example embodiments.

Reference throughout this specification to “one embodiment” or “anembodiment” (or the like) means that a particular feature, structure, orcharacteristic described in connection with the embodiment is includedin at least one embodiment. Thus, the appearance of the phrases “in oneembodiment” or “in an embodiment” or the like in various placesthroughout this specification are not necessarily all referring to thesame embodiment.

Furthermore, the described features, structures, or characteristics maybe combined in any suitable manner in one or more embodiments. In thefollowing description, numerous specific details are provided to give athorough understanding of embodiments. One skilled in the relevant artwill recognize, however, that the various embodiments can be practicedwithout one or more of the specific details, or with other methods,components, materials, et cetera. In other instances, well knownstructures, materials, or operations are not shown or described indetail to avoid obfuscation.

As above, user devices may produce conflicting audio output streams. Forexample, a first user may be watching television when another userenters the room using a smart phone voice call application on speakerphone mode. The audio produced by the television and the smart phoneinterfere with one another, forcing one or both users to adjust thetelevision and smart phone audio outputs.

In an embodiment, a detection of a known device is made. For example,the smart phone in the above example may detect the presence of thetelevision, e.g., via directly communicating with the television, e.g.,via short range wireless communication or indirectly detecting thetelevision, e.g., via a connection with a personal area network. When aknown device, e.g., the television, is detected, an embodiment mayadjust the volume of audio output on the basis of the detection. Theadjustment to the audio output volume may be implemented on one or moredevices, e.g., on just the smart phone, on just the television, on bothof the television and the smart phone, etc. Also, different adjustmentsmay be made (i.e., increase of audio output volume or decrease of audiooutput volume).

An embodiment may determine an audible range of the device(s) indetecting the presence of a know device. This compliments the ability toadjust audio output appropriately, i.e., such that conflicting audio isnot produced or is removed/minimized based on which other device(s) arewithin audible range. For example, an audible range may be apredetermined range, e.g., determined based on the specifications of thedevice, the volume level of the device, the volume level of the contentbeing accessed, etc. For example, a device may estimate its audiblerange based on the frequency of the audio output in combination with avolume level setting. An audio output of lower frequency may travelfarther than a higher frequency output.

An embodiment may determine the context of the audio outputs of deviceswithin the audible range. Devices may share context information with oneanother directly. Moreover, a central or intermediary device mayfacilitate communication between the devices outputting audio, e.g., acloud device or personal area network device may share information withdevices that are present within a given room.

Given the context of a device within a complex audio environment, i.e.,an environment where more than one device is or will be producing audiooutput within the audible range, an embodiment may determine theimportance or priority of a device, a user of the device, or of theaudio output itself (e.g., content). This may be done a variety of ways,e.g., based on the context of the content relative to a user action. Byway of example, an important user action that is given a higher prioritythan other actions may include a user selection dealing with audiooutput volume itself (e.g., increasing, decreasing or muting audio).Such associated user action may be used to determine that a particularaudio stream is or is not a priority audio output.

Based on the context of use, the content, the priority of particulardevices, users, or audio output contents, an embodiment may thereafteradjust the volume of audio output of one or more devices. Thus, anembodiment may automatically lower the audio output of a given device,may increase the audio output of a given device, or a combination of theforegoing. An embodiment may provide a user a notice or a query for auser confirmation of a proposed action prior to implementing anautomated management of the audio output(s).

The illustrated example embodiments will be best understood by referenceto the figures. The following description is intended only by way ofexample, and simply illustrates certain example embodiments.

While various other circuits, circuitry or components may be utilized ininformation handling devices, with regard to smart phone and/or tabletcircuitry 100, an example illustrated in FIG. 1 includes a system on achip design found for example in tablet or other mobile computingplatforms. Software and processor(s) are combined in a single chip 110.Processors comprise internal arithmetic units, registers, cache memory,busses, I/O ports, etc., as is well known in the art. Internal bussesand the like depend on different vendors, but essentially all theperipheral devices (120) may attach to a single chip 110. The circuitry100 combines the processor, memory control, and I/O controller hub allinto a single chip 110. Also, systems 100 of this type do not typicallyuse SATA or PCI or LPC. Common interfaces, for example, include SDIO andI2C.

There are power management chip(s) 130, e.g., a battery management unit,BMU, which manage power as supplied, for example, via a rechargeablebattery 140, which may be recharged by a connection to a power source(not shown). In at least one design, a single chip, such as 110, is usedto supply BIOS like functionality and DRAM memory.

System 100 typically includes one or more of a WWAN transceiver 150 anda WLAN transceiver 160 for connecting to various networks, such astelecommunications networks and wireless Internet devices, e.g., accesspoints. Additionally, devices 120 are commonly included, e.g., an audiooutput device such as a speaker that outputs sound converted fromelectrical signals, as further described herein. System 100 oftenincludes a touch screen 170 for data input and display/rendering. System100 also typically includes various memory devices, for example flashmemory 180 and SDRAM 190.

FIG. 2 depicts a block diagram of another example of informationhandling device circuits, circuitry or components. The example depictedin FIG. 2 may correspond to computing systems such as the THINKPADseries of personal computers sold by Lenovo (US) Inc. of Morrisville,N.C., or other devices. As is apparent from the description herein,embodiments may include other features or only some of the features ofthe example illustrated in FIG. 2.

The example of FIG. 2 includes a so-called chipset 210 (a group ofintegrated circuits, or chips, that work together, chipsets) with anarchitecture that may vary depending on manufacturer (for example,INTEL, AMD, ARM, etc.). INTEL is a registered trademark of IntelCorporation in the United States and other countries. AMD is aregistered trademark of Advanced Micro Devices, Inc. in the UnitedStates and other countries. ARM is an unregistered trademark of ARMHoldings plc in the United States and other countries. The architectureof the chipset 210 includes a core and memory control group 220 and anI/O controller hub 250 that exchanges information (for example, data,signals, commands, etc.) via a direct management interface (DMI) 242 ora link controller 244. In FIG. 2, the DMI 242 is a chip-to-chipinterface (sometimes referred to as being a link between a “northbridge”and a “southbridge”). The core and memory control group 220 include oneor more processors 222 (for example, single or multi-core) and a memorycontroller hub 226 that exchange information via a front side bus (FSB)224; noting that components of the group 220 may be integrated in a chipthat supplants the conventional “northbridge” style architecture. One ormore processors 222 comprise internal arithmetic units, registers, cachememory, busses, I/O ports, etc., as is well known in the art.

In FIG. 2, the memory controller hub 226 interfaces with memory 240 (forexample, to provide support for a type of RAM that may be referred to as“system memory” or “memory”). The memory controller hub 226 furtherincludes a low voltage differential signaling (LVDS) interface 232 for adisplay device 292 (for example, a CRT, a flat panel, touch screen,etc.). A block 238 includes some technologies that may be supported viathe LVDS interface 232 (for example, serial digital video, HDMI/DVI,display port). The memory controller hub 226 also includes a PCI-expressinterface (PCI-E) 234 that may support discrete graphics 236.

In FIG. 2, the I/O hub controller 250 includes a SATA interface 251 (forexample, for HDDs, SDDs, etc., 280), a PCI-E interface 252 (for example,for wireless connections 282), a USB interface 253 (for example, fordevices 284 such as a digitizer, keyboard, mice, cameras, phones,microphones, storage, other connected devices, etc.), a networkinterface 254 (for example, LAN), a GPIO interface 255, a LPC interface270 (for ASICs 271, a TPM 272, a super I/O 273, a firmware hub 274, BIOSsupport 275 as well as various types of memory 276 such as ROM 277,Flash 278, and NVRAM 279), a power management interface 261, a clockgenerator interface 262, an audio interface 263 (for example, forspeakers 294), a TCO interface 264, a system management bus interface265, and SPI Flash 266, which can include BIOS 268 and boot code 290.The I/O hub controller 250 may include gigabit Ethernet support.

The system, upon power on, may be configured to execute boot code 290for the BIOS 268, as stored within the SPI Flash 266, and thereafterprocesses data under the control of one or more operating systems andapplication software (for example, stored in system memory 240). Anoperating system may be stored in any of a variety of locations andaccessed, for example, according to instructions of the BIOS 268. Asdescribed herein, a device may include fewer or more features than shownin the system of FIG. 2.

Information handling device circuitry, as for example outlined in FIG. 1or FIG. 2, may be used in devices such as tablets, smart phones,personal computer devices generally, and/or electronic devices thatusers may to use to produce audio outputs, for example associated withconsuming media files, using voice call applications, producing devicenotifications (such as alarm clocks, ring tone or chimes used toindicate incoming communications such as emails, text messages and thelike), etc. Specifically, an embodiment may be implemented as a deviceapplication running on one or more of a user's personal electronicdevices.

Referring to FIG. 3, a device may determine, at 310, its audible rangeand/or the audible range of surrounding device(s). The audible range maybe determined by default, e.g., set according to specifications of thedevice or a sub-system or component thereof (e.g., speakerspecifications). The audible range may be determined automatically in adynamic fashion, e.g., using operative settings information such asvolume level or the type (e.g., frequency) of the content currentlybeing played. This information may then be converted into an audiblerange. A combination of specifications and setting information may beutilized to determine the audible range of the device. While notexplicitly illustrated, the audible range calculated or otherwise set ordetermined for or by a device may be shared with other devices, e.g.,within the calculated audible range, within a listing of personaldevices, etc., such that the devices are aware of one another's audibleranges. In an embodiment, the audible range may be inferred, e.g., asinclusive of devices within a short range network such as connected viaBLUETOOTH communication.

At 320 an embodiment may determine if a known device (e.g., another userdevice within a personal area network) is within audible range. Forexample, a user's smart phone may detect the presence of the user'stelevision set, e.g., via short range wireless communication directlybetween the smart phone and the television set. Alternatively, the smartphone may detect the presence of the television via communication withan intermediary device, e.g., the user's laptop or a remote device, suchas a cloud server.

An embodiment may determine, at 330 and based on the devices within theaudible range, a context of the audio output stream(s) of the deviceswithin that range. By way of example, devices may share contextinformation with one another, e.g., regarding their location, theirpriority (as devices), the priority of their audio outputs (based on thecontent thereof), etc. Devices may share such information directly ormay share this information via an intermediary or managing device.

Illustrated at 340, an embodiment may determine the importance orpriority of a given audio output within the audible range. By way ofexample, the importance of the device, the content (e.g., content type,such as work, casual conversation, movie or television program, etc.),the associated function (e.g., alarm clock versus streaming radioprogram), or a user associated with the device may be determined. Thus,a device operating an alarm clock function or timer function for audiooutput may be prioritized over a device streaming a television or radioprogram. Likewise, a particular user device, e.g., a television set, maybe prioritized over another user device, e.g., a child's media player ortablet. Based on the relative priority, one or more of the audio streamsmay be adjusted at 350.

An embodiment employs context in intelligently managing the volume ofdevice audio outputs automatically. An embodiment may link certainfunctions with a priority setting (e.g., high priority) such that theydo not have their volumes adjusted downward. For example, initiating orreceiving a phone call, actions related to adjusting the volumemanually, other manual user actions (e.g., changing a televisionchannel), initiating new content playback on a device, etc., may begiven a higher priority or ranking than other audio outputs, e.g.,existing media playback on another device. An embodiment may also useother information to infer the context, priority, and appropriateadjustments. For example, an embodiment may determine context based on arelative or absolute values, e.g., a user or manufacturer may setpriority for devices such that incoming phone calls are prioritized interms of audio output over television or music playback. Likewise, usersmay set priorities of devices. Priorities or rankings may be employed ina variety of ways, for example ranking users, content and/or devices interms of audio output. By way of example, parents' devices may beprioritized over or ranked higher than children's devices, or viceversa, certain content types may be prioritized over or ranked higherthan others, e.g., movies ranked higher than cartoons, etc. Amulti-factor analysis may be employed, e.g., taking into account adevice ranking and a content type ranking.

An embodiment may adjust the volume(s) of the audio output(s)automatically at 350. The adjustment may be a locally implementedadjustment, i.e., a device may adjust its own volume up or down,depending on the other device(s) known to be within audible range, theirpriorities, etc. An adjustment to the volume may also be implementedremotely, e.g., a device may issue an instruction to another device(either directly or indirectly) to adjust that other device's volume.Similarly, a master device may issue instructions to some or all of thedevices within the audible range.

An embodiment uses an importance determination at 340 to implement theadjustment at 350. The adjustment may include muting the volume,reducing the volume, or increasing the volume. The adjustment may takeinto account the device's audible range, e.g., reducing the volume to alevel that takes the device out of the audible range with respect toanother device (e.g., a higher priority device). Moreover, theadjustment may be incremental or dynamic, e.g., adjusted more than once,such as when another device changes its volume of audio output, as thedevice enters and/or leaves the audible range, etc. The determination ofwhether to adjust the volume of a given device may also depend on theoutput channel utilized by the device, e.g., a device outputting audioto a headset may not be subjected to automated volume adjustment.

The adjusted volume may be implemented automatically; however, this isnot a requirement. In an embodiment, a notification may be provided tothe user of the device such that the user is aware that a volumeadjustment (for the user's device or another device) is recommended. Forexample, an embodiment may provide the user with an option, e.g., toanswer a call and mute all other devices within audible range. As withother audio adjustments, this may be temporary, e.g., linked in timewith the ongoing voice call, the device's presence within the audiblerange, etc.

As will be appreciated by one skilled in the art, various aspects may beembodied as a system, method or device program product. Accordingly,aspects may take the form of an entirely hardware embodiment or anembodiment including software that may all generally be referred toherein as a “circuit,” “module” or “system.” Furthermore, aspects maytake the form of a device program product embodied in one or more devicereadable medium(s) having device readable program code embodiedtherewith.

It should be noted that the various functions described herein may beimplemented using instructions stored on a device readable storagemedium such as a non-signal storage device that are executed by aprocessor. A storage device may be, for example, an electronic,magnetic, optical, electromagnetic, infrared, or semiconductor system,apparatus, or device, or any suitable combination of the foregoing. Morespecific examples of a storage medium would include the following: aportable computer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), an optical fiber, a portable compact disc read-onlymemory (CD-ROM), an optical storage device, a magnetic storage device,or any suitable combination of the foregoing. In the context of thisdocument, a storage device is not a signal and “non-transitory” includesall media except signal media.

Program code embodied on a storage medium may be transmitted using anyappropriate medium, including but not limited to wireless, wireline,optical fiber cable, RF, et cetera, or any suitable combination of theforegoing.

Program code for carrying out operations may be written in anycombination of one or more programming languages. The program code mayexecute entirely on a single device, partly on a single device, as astand-alone software package, partly on single device and partly onanother device, or entirely on the other device. In some cases, thedevices may be connected through any type of connection or network,including a local area network (LAN) or a wide area network (WAN), orthe connection may be made through other devices (for example, throughthe Internet using an Internet Service Provider), through wirelessconnections, e.g., near-field communication, or through a hard wireconnection, such as over a USB connection.

Example embodiments are described herein with reference to the figures,which illustrate example methods, devices and program products accordingto various example embodiments. It will be understood that the actionsand functionality may be implemented at least in part by programinstructions. These program instructions may be provided to a processorof a device, a special purpose information handling device, or otherprogrammable data processing device to produce a machine, such that theinstructions, which execute via a processor of the device implement thefunctions/acts specified.

It is worth noting that while specific blocks are used in the figures,and a particular ordering of blocks has been illustrated, these arenon-limiting examples. In certain contexts, two or more blocks may becombined, a block may be split into two or more blocks, or certainblocks may be re-ordered or re-organized as appropriate, as the explicitillustrated examples are used only for descriptive purposes and are notto be construed as limiting.

As used herein, the singular “a” and “an” may be construed as includingthe plural “one or more” unless clearly indicated otherwise.

This disclosure has been presented for purposes of illustration anddescription but is not intended to be exhaustive or limiting. Manymodifications and variations will be apparent to those of ordinary skillin the art. The example embodiments were chosen and described in orderto explain principles and practical application, and to enable others ofordinary skill in the art to understand the disclosure for variousembodiments with various modifications as are suited to the particularuse contemplated.

Thus, although illustrative example embodiments have been describedherein with reference to the accompanying figures, it is to beunderstood that this description is not limiting and that various otherchanges and modifications may be affected therein by one skilled in theart without departing from the scope or spirit of the disclosure.

1. A method, comprising: detecting, using a processor, a presence of a known device within a predetermined range; and adjusting, using a processor, an audio output volume based on the presence of the known device.
 2. The method of claim 1, wherein the detecting comprises detecting the known device via a personal area network.
 3. The method of claim 1, wherein the detecting comprises detecting the known device via short range wireless communication.
 4. The method of claim 1, wherein the detecting comprises receiving a priority indication.
 5. The method of claim 4, wherein the adjusting comprises determining if the priority indication dictates a lower volume.
 6. The method of claim 5, wherein the adjusting comprises lowering the audio output volume.
 7. The method of claim 1, further comprising determining a content type; wherein the adjusting comprises adjusting the audio output volume based on the presence of the known device and the content type.
 8. The method of claim 7, wherein the content type is derived from content analysis.
 9. The method of claim 1, wherein the adjusting comprises issuing an instruction to the known device.
 10. The method of claim 1, wherein the audio output volume is adjusted locally.
 11. A device, comprising: a processor; an audio output device operatively coupled to the processor; a memory device that stores instructions executable by the processor to: detect a presence of a known device within a predetermined range; and adjusting, using the processor, an audio output volume based on the presence of the known device.
 12. The device of claim 11, wherein to detect comprises detecting the known device via a personal area network.
 13. The device of claim 11, wherein to detect comprises detecting the known device via short range wireless communication.
 14. The device of claim 11, wherein to detect comprises receiving a priority indication.
 15. The device of claim 14, wherein to adjust comprises determining if the priority indication dictates a lower volume.
 16. The device of claim 15, wherein to adjust comprises lowering the audio output volume.
 17. The device of claim 11, wherein the instructions are executable by the processor to determine a content type; and wherein to adjust comprises adjusting the audio output volume based on the presence of the known device and the content type.
 18. The device of claim 17, wherein the content type is derived from content analysis.
 19. The device of claim 11, wherein to adjust comprises issuing an instruction to the known device.
 20. A product, comprising: a storage device having code stored therewith, the code being executable by a processor and comprising: code that detects a presence of a known device within a predetermined range; and code that adjusts an audio output volume based on the presence of the known device. 